Skip to content

Add FontAwesome token to CI workflow - #76

Merged
MarcinZiabek merged 1 commit into
mainfrom
MarcinZiabek-patch-2
Nov 3, 2026
Merged

MarcinZiabek merged 1 commit into
mainfrom
MarcinZiabek-patch-2

Conversation

@MarcinZiabek

Copy link
Copy Markdown
Member

Redesigns the homepage and the pricing, license, features overview and contact pages on one shared visual system, in light and dark.

  • Homepage: rebuilt with a new hero, CTA cards, Quick Start demo, and Companion, Trust and License sections.
  • Pricing: restyled tiers, and the FAQ is now grouped by topic. Prices, FAQ answers and legal text are unchanged.
  • Features overview: rebuilt with an icon and description for each feature.
  • Under the hood: Font Awesome now comes from npm packages instead of the kit script, code is highlighted at build time with Shiki, images moved to WebP, and 145 unused files are removed.

Builds now need FONTAWESOME_NPM_AUTH_TOKEN, in CI and in production.

Add FontAwesome NPM auth token to environment variables for dependency installation.
Copilot AI balanced review requested due to automatic review settings November 3, 2026 16:28
@MarcinZiabek
MarcinZiabek merged commit 06748bb into main Nov 3, 2026
2 checks passed

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

There are no active review issues for the workflow change that supplies the Font Awesome npm authentication token.

No open issues 🎉

What changed in this PR

Updates CI dependency installation to support the Font Awesome npm packages required by the site redesign. This diff only changes the workflow, not the pages described in the PR.

Changes:

  • Passes the FONTAWESOME_NPM_AUTH_TOKEN repository secret to the npm ci step.
File Description
.github/​workflows/​main.yml Supplies the Font Awesome authentication token during dependency installation.

Review effort: Balanced

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants